<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
 <head>
  <meta content="Copyright &copy; 2023 Thales. All Rights Reserved." name="copyright"/>
  <meta content="text/html;charset=utf-8" http-equiv="content-type"/>
  <meta content="text/css" http-equiv="Content-Style-Type"/>
  <title>
   Arcadia Reference - Define Architectural Principles and Patterns
  </title>
  <link href="../../scripts/jquery-treeview/jquery.treeview.css" rel="stylesheet"/>
  <script src="../../scripts/jquery-treeview/lib/jquery-1.11.1.js" type="text/javascript">
  </script>
  <script src="../../scripts/jquery-treeview/jquery.treeview.js" type="text/javascript">
  </script>
  <link href="../../css/simpletree.css" rel="stylesheet" type="text/css"/>
  <link href="../../css/content.css" media="screen, projection" rel="stylesheet" title="default" type="text/css"/>
  <style>
   body {}
			.treeview {
				background-color: white ;
			}
	
			.treeview ul{ /*CSS for Simple Tree Menu*/
				background-color: white;
				font-size: 12px;
			}
	
			.treeview li{ /*Style for LI elements in general (excludes an LI that contains sub lists)*/
				background-color: white;
			}
  </style>
 </head>
 <body>
  <img src="../icon/logo_arcadia_small.png" style="float:left;width:50px;height:50px;"/>
  <nav>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#">
    ARCADIA
   </a>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#landscape">
    Engineering Landscape
   </a>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#userGuide">
    User Guide
   </a>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#reference">
    Reference Manual
   </a>
  </nav>
  <p>
   <br/>
  </p>
  <div id="content">
   <img alt="PhysicalFunction" src="../icon/PhysicalFunction.png" style="float:left; margin-right:10px"/>
   <h1>
    <a href="../ARCADIA/e7c795b3dd09496bafd2677462a6e23d.html">
     Define Architectural Principles and Patterns
    </a>
   </h1>
   <p style="margin-top:3px; margin-bottom:3px">
    <span class="elementMetaClass">
     Engineering activity
    </span>
    <p>
    </p>
   </p>
   <em class="elementPath">
    <a href="../ARCADIA/6a3284b8a66748a597631eb95e8e8c55.html">
     Engineering activities
    </a>
    &gt;
    <a href="../ARCADIA/bd6945b4ae34413581335ae6b6f6f503.html">
     Engineering Activities &amp; Perspectives
    </a>
    &gt;
    <a href="../ARCADIA/caca5154f8a94592ba0d4513a6141c46.html">
     DESIGN THE SOLUTION ARCHITECTURE
    </a>
    &gt;
    <a href="../ARCADIA/38c7424f5c11476490db367b0b43bc42.html">
     Design PHYSICAL ARCHITECTURE
    </a>
    &gt;
    <a href="../ARCADIA/e7c795b3dd09496bafd2677462a6e23d.html">
     Define Architectural Principles and Patterns
    </a>
   </em>
   <p>
    <p>
     Identify architecture Invariants (common and generic behaviours, interfaces, functions, services, &hellip;) that simplify definition, implementation, development and integration of the system/software, by reducing diversity and heterogeneity of features in the architecture. These are called architectural Patterns.
    </p>
    <p>
     &nbsp;
    </p>
    <ul>
     <li>
      Rationalisation components &amp; functions: search for similarities in logical architecture analysis (e.g. a data server simplifying communications of a highly shared data set, common and generic hardware computing core, data transformation library&hellip;)
     </li>
    </ul>
    <p>
     &nbsp;
    </p>
    <ul>
     <li>
      Technical functions and services: in order to support common behaviours and properties expected from the architecture (e.g. communication services, components lifecycle, supervision/surveillance, reconfiguration means, test &amp; observability probes&hellip;)
     </li>
    </ul>
    <p>
     &nbsp;
    </p>
    <ul>
     <li>
      Technological patterns: driven by technology and state-of-the-art in architecting and hardware/software technology (e.g. component model, client-server paradigm, hardware FFT computing resource).
     </li>
    </ul>
    <p>
     &nbsp;
    </p>
    <p>
     These modelling concepts may be considered as catalogue elements providing parts of models of efficient architectural solutions to be adapted to target components. The use of architectural patterns is of great benefit for easing separation of concerns, unifying behaviour, supporting internal standards e.g. component-based design, communication means, system-level common services&hellip;
    </p>
    <p>
     &nbsp;
    </p>
    <p>
     Standards compliance should be sought as much as possible, while checking their real adequacy to the planned use in the system/software.
    </p>
    <p>
     &nbsp;
    </p>
    <h2>
     Input:
    </h2>
    <ul>
     <li>
      state-of-the-art architectural patterns (e.g. components (containers), services..., real-time architectures &amp; concepts (RMA, queuing networks&hellip;)
     </li>
     <li>
      Standards
     </li>
    </ul>
    <p>
     &nbsp;
    </p>
    <h2>
     Output
    </h2>
    <ul>
     <li>
      Architectural patterns applicable to the target architecture (including interfaces)
     </li>
     <li>
      Selection of Architectural patterns to be applied to logical/physical components and/or their interfaces
     </li>
    </ul>
    <p>
     Target documents:
    </p>
    <ul>
     <li>
      System/Segment Design Document (SSDD)
     </li>
    </ul>
    <p>
     &nbsp;
    </p>
    <h2>
     Verification and Consistency checks
    </h2>
    <p>
     <em>
      External consistency:
     </em>
    </p>
    <ul>
     <li>
      Between domain (User Requirements, non-functional constraints) and applicable standards / patterns
     </li>
    </ul>
    <p>
     <em>
      Internal consistency:
     </em>
    </p>
    <ul>
     <li>
      Between Architectural patterns &amp; standards
     </li>
    </ul>
    <p>
     &nbsp;
    </p>
   </p>
   <h2>
    Diagrams displaying "Define Architectural Principles and Patterns"
   </h2>
   <ul>
    <li>
     <a href="../ARCADIA/38c7424f5c11476490db367b0b43bc42.html#_pM66YHcaEe2lVaNV4qOrAA">
      2-Design PHYSICAL ARCHITECTURE - Contents
     </a>
    </li>
    <li>
     <a href="../ARCADIA/6a3284b8a66748a597631eb95e8e8c55.html#_W8OfUHccEe2lVaNV4qOrAA">
      4 - Customer Work
     </a>
    </li>
    <li>
     <a href="../ARCADIA/3982ff6dbae645c6894cb6500418e194.html#_MTe0cHcbEe2lVaNV4qOrAA">
      3-Build candidate detailled Architectures - Context
     </a>
    </li>
    <li>
     <a href="../ARCADIA/6a3284b8a66748a597631eb95e8e8c55.html#_ad5Z0HcdEe2lVaNV4qOrAA">
      5 - Models Management
     </a>
    </li>
    <li>
     <a href="../ARCADIA/6a3284b8a66748a597631eb95e8e8c55.html#_HvCG8HcdEe2lVaNV4qOrAA">
      4 - Sub-contractor Work
     </a>
    </li>
    <li>
     <a href="../ARCADIA/6a3284b8a66748a597631eb95e8e8c55.html#_jOY0gHccEe2lVaNV4qOrAA">
      4 - IVVQ Manager Work
     </a>
    </li>
    <li>
     <a href="../ARCADIA/0a87fdb64bde4217a0e88226c1ec65bc.html#_p79DQHcdEe2lVaNV4qOrAA">
      Modelling Support Tooling
     </a>
    </li>
    <li>
     <a href="../ARCADIA/6a3284b8a66748a597631eb95e8e8c55.html#_xlkVcHccEe2lVaNV4qOrAA">
      4 - Non functional Specialty Engineering Work
     </a>
    </li>
    <li>
     <a href="../ARCADIA/6a3284b8a66748a597631eb95e8e8c55.html#_ddwSoHccEe2lVaNV4qOrAA">
      4 - Data &amp; Interface Manager Work
     </a>
    </li>
    <li>
     <a href="../ARCADIA/6a3284b8a66748a597631eb95e8e8c55.html#_2z-7EHccEe2lVaNV4qOrAA">
      4 - Product Line &amp; Configuration Managers Work
     </a>
    </li>
    <li>
     <a href="../ARCADIA/6a3284b8a66748a597631eb95e8e8c55.html#_d5BkQHcaEe2lVaNV4qOrAA">
      1 - First Level Tasks of Architecture Definition Perspectives
     </a>
    </li>
    <li>
     <a href="../ARCADIA/6a3284b8a66748a597631eb95e8e8c55.html#_PJdGkHccEe2lVaNV4qOrAA">
      4 - Chief Architect Work
     </a>
    </li>
   </ul>
  </div>
 </body>
</html>
